Blockchain-based system that records the states of 5g end user mobile devices using the distributed ledger

ABSTRACT

Embodiments are directed towards systems and methods for implementing a blockchain-based state database using a distributed ledger. One such method includes: recording states of one or more 5G end user mobile devices in any 5G network RAN or Core element in a state database using the distributed ledger of the blockchain; in response to a lost connection of a network element, restoring, using the blockchain database, the lost connection of the network element to the network without any interaction with the 5G end user mobile device; accessing the recorded states of the one or more 5G end user mobile devices in the state database on the distributed ledger of the blockchain; and reestablishing the recorded states of the one or more 5G end user mobile devices using the recorded states from the state database in the distributed ledger of the blockchain.

BACKGROUND

As the use of smart phones and Internet of Things (IoT) devices hasincreased, so too has the desire for more reliable, fast, and continuoustransmission of content. In an effort to improve the contenttransmission, networks continue to improve with faster speeds andincreased bandwidth. The advent and implementation of Fifth Generation(5G) wireless technology has resulted in faster speeds and increasedbandwidth. Thus, minimizing interruptions in the supporting networkinginfrastructure is important to providing a resilient and stable networkwith the desired end-to-end performance. It is with respect to these andother considerations that the embodiments described herein have beenmade.

In some types of 5G network architecture, multiple 5G Cores areconnected to a central database that manages subscriber information.During operation of the 5G network, there may be occasions whenconnections between one or more of the 5G Cores and the central databaseare disrupted or otherwise lost, due to power outages or other reasons.When a connection loss or other type of failure occurs, stateful 5G enduser mobile devices are severely compromised in their ability to carryout any significant cellular telephone communication activities sincestate information is required for many cellular telephone communicationactivities in 5G telephony communication. Determining a way to maintainstate information after a connection loss is a current technologicalchallenge in need of a technological solution. The present disclosureaddresses this and other issues.

BRIEF SUMMARY

The present disclosure relates generally to telecommunication networks,more particularly, to managing 5G telecommunication networks andreestablishing state information after connection loss.

5G provides a broad range of wireless services delivered to the end useracross multiple access platforms and multi-layer networks. 5G is adynamic, coherent and flexible framework of multiple advancedtechnologies supporting a variety of applications. 5G utilizes anintelligent architecture, with Radio Access Networks (RANs) notconstrained by base station proximity or complex infrastructure. 5Genables a disaggregated, flexible, and virtual RAN with interfacescreating additional data access points.

5G network functions may be completely software-based and designed ascloud-native, meaning that they're agnostic to the underlying cloudinfrastructure, allowing higher deployment agility and flexibility.

With the advent of 5G, industry experts defined how the 5G Core (5GC)network should evolve to support the needs of 5G New Radio (NR) and theadvanced use cases enabled by it. The 3rd Generation Partnership Project(3GPP) develops protocols and standards for telecommunicationtechnologies including RAN, core transport networks and servicecapabilities. 3GPP has provided complete system specifications for 5Gnetwork architecture which is much more service oriented than previousgenerations.

Multi-Access Edge Computing (MEC) is an important element of 5Garchitecture. MEC is an evolution in Telecommunications that brings theapplications from centralized data centers to the network edge, andtherefore closer to the end users and their devices. This essentiallycreates a shortcut in content delivery between the user and host, andthe long network path that once separated them.

This MEC technology is not exclusive to 5G but is certainly important toits efficiency. Characteristics of the MEC include the low latency, highbandwidth and real time access to RAN information that distinguishes 5Garchitecture from its predecessors. This convergence of the RAN and corenetworks enables operators to leverage new approaches to network testingand validation. 5G networks based on the 3GPP 5G specifications providean environment for MEC deployment. The 5G specifications define theenablers for edge computing, allowing MEC and 5G to collaborativelyroute traffic. In addition to the latency and bandwidth benefits of theMEC architecture, the distribution of computing power better enables thehigh volume of connected devices inherent to 5G deployment and the riseof IoT.

The 3rd Generation Partnership Project (3GPP) develops protocols formobile telecommunications and has developed a standard for 5G. The 5Garchitecture is based on what is called a Service-Based Architecture(SBA), which leverages IT development principles and a cloud-nativedesign approach. In this architecture, each network function (NF) offersone or more services to other NFs via Application Programming Interfaces(API). Network function virtualization (NFV) decouples software fromhardware by replacing various network functions such as firewalls, loadbalancers and routers with virtualized instances running as software.This eliminates the need to invest in many expensive hardware elementsand can also accelerate installation times, thereby providing revenuegenerating services to the customer faster.

NFV enables the 5G infrastructure by virtualizing appliances within the5G network. This includes the network slicing technology that enablesmultiple virtual networks to run simultaneously. NFV may address other5G challenges through virtualized computing, storage, and networkresources that are customized based on the applications and customersegments. The concept of NFV extends to the RAN through, for example,network disaggregation promoted by alliances such as O-RAN. This enablesflexibility, provides open interfaces and open-source development,ultimately to ease the deployment of new features and technology withscale. The O-RAN ALLIANCE objective is to allow multi-vendor deploymentwith off-the shelf hardware for the purposes of easier and fasterinter-operability. It is however the use of off the shelf technologywhich introduces the challenge of maintaining state. Traditionaltelecommunication equipment suppliers used purpose built, fullyredundant equipment. Application software could rely on the redundancyof the hardware to maintain state information. In an O-RAN environment,state must be maintained in a new, scalable way. Network disaggregationalso allows components of the network to be virtualized, providing ameans to scale and improve user experience as capacity grows. Thebenefits of virtualizing components of the RAN provide a means to bemore cost effective from a hardware and software viewpoint especiallyfor IoT applications where the number of devices is in the millions.

The 5G New Radio (5G NR) RAN comprises a set of radio base stations(each known as Next Generation Node B (gNB)) connected to the 5G Core(5GC) and to each other. The gNB incorporates three main functionalmodules: the Centralized Unit (CU), the distributed Unit (DU), and theRadio Unit (RU), which can be deployed in multiple combinations. Theprimary interface is referred to as the F1 interface between DU and CUand are interoperable across vendors. The CU may be furtherdisaggregated into the CU user plane (CU-UP) and CU control plane(CU-CP), both of which connect to the DU over F1-U and F1-C interfacesrespectively. This 5G RAN architecture is described in 3GPP TS 38.401V16.8.0 (2021-12). Each network function (NF) is formed by a combinationof small pieces of software code called microservices.

Briefly stated, one or more methods for implementing a blockchain-basedstate database using a distributed ledger are disclosed. Some suchmethods include: providing, by a mobile network operator, a distributedunit (DU) of a fifth-generation New Radio (5G NR) cellulartelecommunication network radio access network (RAN) that is served by aparticular 5G NR cellular site base station, wherein the DU: isassociated with a primary 5G NR Next Generation Node B (gNB) identifiedby a primary identifier (ID); and is in operable communication with acorresponding primary central unit control plane (CU-CP) of a 5G NRprimary centralized unit (CU) that is hosted on a cloud-nativevirtualized compute instance in a primary cloud availability zone and isalso associated with the primary gNB identified by the primary ID;providing, by a mobile network operator, a distributed unit (DU) of afifth-generation New Radio (5G NR) cellular telecommunication networkradio access network (RAN) that is served by a particular 5G NR cellularsite base station, wherein the DU: is associated with a primary 5G NRNext Generation Node B (gNB) identified by a primary identifier (ID);and is in operable communication with a corresponding primary centralunit control plane (CU-CP) of a 5G NR primary centralized unit (CU) thatis hosted on a cloud-native virtualized compute instance in a primarycloud availability zone and is also associated with the primary gNBidentified by the primary ID; providing a Unified Data Management systemthat includes a Distributed Subscriber Database and connects to aplurality of 5G Cores, wherein each 5G Core in turn connects to one ormore 5G end user mobile devices; recording states of one or more 5G enduser mobile devices in any 5G network RAN or Core element in a statedatabase using the distributed ledger of the blockchain; in response toa lost connection of a network element, restoring, using the blockchaindatabase, the lost connection of the network element to the networkwithout any interaction with the 5G end user mobile device; accessingthe recorded states of the one or more 5G end user mobile devices in thestate database on the distributed ledger of the blockchain; andreestablishing the recorded states of the one or more 5G end user mobiledevices using the recorded states from the state database in thedistributed ledger of the blockchain.

In some embodiments of the methods for implementing a blockchain-basedstate database using a distributed ledger, the method further includesconnecting each individual 5G end user mobile device to an associated 5GCore using an IMSI (International Mobile Subscriber Identifier) number.In another aspect of some embodiments, the method further includesidentifying a mobile subscriber of each individual 5G end user mobiledevice by its SIM (Subscriber Identity Module) card. In still anotheraspect of some embodiments, the blockchain-based state database isoptimized for performance. In yet another aspect of some embodiments,the blockchain-based state database is optimized for reliability. Also,in one or more aspects of some embodiments, the distributed keyauthentication is used to authenticate the 5G end user mobile device.Furthermore, in some embodiments, the distributed keys are placed in theblockchain with the recorded state information.

In other embodiments, one or more systems for implementing ablockchain-based state database using a distributed ledger aredisclosed. The system includes: a memory that stores computer executableinstructions; and a processor that executes the computer executableinstructions to: provide, by a mobile network operator, a distributedunit (DU) of a fifth-generation New Radio (5G NR) cellulartelecommunication network radio access network (RAN) that is served by aparticular 5G NR cellular site base station, wherein the DU: isassociated with a primary 5G NR Next Generation Node B (gNB) identifiedby a primary identifier (ID); and is in operable communication with acorresponding primary central unit control plane (CU-CP) of a 5G NRprimary centralized unit (CU) that is hosted on a cloud-nativevirtualized compute instance in a primary cloud availability zone and isalso associated with the primary gNB identified by the primary ID;provide a Unified Data Management system that includes a DistributedSubscriber Database and connects to a plurality of 5G Cores, whereineach 5G Core in turn connects to one or more 5G end user mobile devices;record states of one or more 5G end user mobile devices in any 5Gnetwork RAN or Core element in a state database using the distributedledger of the blockchain; in response to a lost connection of a networkelement, restore, using the blockchain database, the lost connection ofthe network element to the network without any interaction with the 5Gend user mobile device; access the recorded states of the one or more 5Gend user mobile devices in the state database on the distributed ledgerof the blockchain; and reestablish the recorded states of the one ormore 5G end user mobile devices using the recorded states from the statedatabase in the distributed ledger of the blockchain.

In some embodiments of the systems for implementing a blockchain-basedstate database using a distributed ledger, the system further includesconnecting each individual 5G end user mobile device to an associated 5GCore using an IMSI (International Mobile Subscriber Identifier) number.In another aspect of some embodiments, the system further includesidentifying a mobile subscriber of each individual 5G end user mobiledevice by its SIM (Subscriber Identity Module) card. In still anotheraspect of some embodiments, the blockchain-based state database isoptimized for performance. In yet another aspect of some embodiments,the blockchain-based state database is optimized for reliability. Also,in one or more aspects of some embodiments, the distributed keyauthentication is used to authenticate the 5G end user mobile device.Furthermore, in some embodiments, the distributed keys are placed in theblockchain with the recorded state information.

Additionally, in other embodiments, one or more non-transitorycomputer-readable storage mediums are disclosed. The one or morenon-transitory computer-readable storage mediums havecomputer-executable instructions stored thereon that, when executed by aprocessor, cause the processor to: provide, by a mobile networkoperator, a distributed unit (DU) of a fifth-generation New Radio (5GNR) cellular telecommunication network radio access network (RAN) thatis served by a particular 5G NR cellular site base station, wherein theDU: is associated with a primary 5G NR Next Generation Node B (gNB)identified by a primary identifier (ID); and is in operablecommunication with a corresponding primary central unit control plane(CU-CP) of a 5G NR primary centralized unit (CU) that is hosted on acloud-native virtualized compute instance in a primary cloudavailability zone and is also associated with the primary gNB identifiedby the primary ID; provide a Unified Data Management system thatincludes a Distributed Subscriber Database and connects to a pluralityof 5G Cores, wherein each 5G Core in turn connects to one or more 5G enduser mobile devices; record states of one or more 5G end user mobiledevices in any 5G network RAN or Core element in a state database usingthe distributed ledger of the blockchain; in response to a lostconnection of a network element, restore, using the blockchain database,the lost connection of the network element to the network without anyinteraction with the 5G end user mobile device; access the recordedstates of the one or more 5G end user mobile devices in the statedatabase on the distributed ledger of the blockchain; and reestablishthe recorded states of the one or more 5G end user mobile devices usingthe recorded states from the state database in the distributed ledger ofthe blockchain.

In some embodiments, the non-transitory computer-readable storage mediumfor implementing a blockchain-based state database using a distributedledger includes connecting each individual 5G end user mobile device toan associated 5G Core using an IMSI (International Mobile SubscriberIdentifier) number. In another aspect of some embodiments, thenon-transitory computer-readable storage medium further includesidentifying a mobile subscriber of each individual 5G end user mobiledevice by its SIM (Subscriber Identity Module) card. In still anotheraspect of some embodiments, the blockchain-based state database isoptimized for performance. In yet another aspect of some embodiments,the blockchain-based state database is optimized for reliability. Also,in one or more aspects of some embodiments, the distributed keyauthentication is used to authenticate the 5G end user mobile device.Furthermore, in some embodiments, the distributed keys are placed in theblockchain with the recorded state information.

Furthermore, in other embodiments, one or more methods for implementinga blockchain-based state database using a distributed ledger aredisclosed. Some such methods include: recording states of one or more 5Gend user mobile devices in any 5G network RAN or Core element in a statedatabase using the distributed ledger of the blockchain; in response toa lost connection of a network element, restoring, using the blockchaindatabase, the lost connection of the network element to the networkwithout any interaction with the 5G end user mobile device; accessingthe recorded states of the one or more 5G end user mobile devices in thestate database on the distributed ledger of the blockchain; andreestablishing the recorded states of the one or more 5G end user mobiledevices using the recorded states from the state database in thedistributed ledger of the blockchain.

Moreover, in still other embodiments, one or more systems forimplementing a blockchain-based state database using a distributedledger are disclosed. Some such systems include: a memory that storescomputer executable instructions; and a processor that executes thecomputer executable instructions to: record states of one or more 5G enduser mobile devices in any 5G network RAN or Core element in a statedatabase using the distributed ledger of the blockchain; in response toa lost connection of a network element, restore, using the blockchaindatabase, the lost connection of the network element to the networkwithout any interaction with the 5G end user mobile device; access therecorded states of the one or more 5G end user mobile devices in thestate database on the distributed ledger of the blockchain; andreestablish the recorded states of the one or more 5G end user mobiledevices using the recorded states from the state database in thedistributed ledger of the blockchain.

Additionally, in other embodiments, one or more non-transitorycomputer-readable storage mediums are disclosed. The one or morenon-transitory computer-readable storage mediums havecomputer-executable instructions stored thereon that, when executed by aprocessor, cause the processor to: record states of one or more 5G enduser mobile devices in any 5G network RAN or Core element in a statedatabase using the distributed ledger of the blockchain; in response toa lost connection of a network element, restore, using the blockchaindatabase, the lost connection of the network element to the networkwithout any interaction with the 5G end user mobile device; access therecorded states of the one or more 5G end user mobile devices in thestate database on the distributed ledger of the blockchain; andreestablish the recorded states of the one or more 5G end user mobiledevices using the recorded states from the state database in thedistributed ledger of the blockchain.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments are described with referenceto the following drawings. In the drawings, like reference numeralsrefer to like parts throughout the various figures unless otherwisespecified.

For a better understanding of the present invention, reference will bemade to the following Detailed Description, which is to be read inassociation with the accompanying drawings:

FIG. 1 illustrates a context diagram of an environment for a system thatimplements a blockchain-based state database using a distributed ledger,in accordance with embodiments described herein.

FIG. 2 illustrates a diagram of an example system architecture overviewof a system in which the environment of FIG. 1 may be implemented inaccordance with embodiments described herein.

FIG. 3 illustrates a diagram showing connectivity between certain 5Gtelecommunication network components during 5G cellulartelecommunication.

FIG. 4A illustrates a system that includes a central distributedsubscriber database, a plurality of connected 5G Cores, and a pluralityof end user mobile devices connected to each 5G Core.

FIG. 4B illustrates the system shown in FIG. 4A where the distributedsubscriber database has lost connection with one or more of the 5Gmobile end-user devices.

FIG. 4C illustrates the system shown in FIG. 4A where the distributedsubscriber database has re-established connection with the one or moreof the 5G mobile end-user devices that had previously lost theirconnection with the distributed subscriber database.

FIG. 5 illustrates a logic diagram that shows the process of uploadingstate information to the distributed ledger of the blockchain that isthen available to the plurality of 5G mobile end-user devices.

FIG. 6 is a logic diagram showing state recording data flow betweencertain telecommunication network components during upload to theblockchain and distribution to the 5G mobile end-user devices.

FIG. 7 shows a system diagram that describes an example implementationof a computing system(s) for implementing embodiments described herein.

DETAILED DESCRIPTION

The following description, along with the accompanying drawings, setsforth certain specific details in order to provide a thoroughunderstanding of various disclosed embodiments. However, one skilled inthe relevant art will recognize that the disclosed embodiments may bepracticed in various combinations, without one or more of these specificdetails, or with other methods, components, devices, materials, etc. Inother instances, well-known structures or components that are associatedwith the environment of the present disclosure, including but notlimited to the communication systems and networks, have not been shownor described in order to avoid unnecessarily obscuring descriptions ofthe embodiments. Additionally, the various embodiments may be methods,systems, media, or devices. Accordingly, the various embodiments may beentirely hardware embodiments, entirely software embodiments, orembodiments combining software and hardware aspects.

Throughout the specification, claims, and drawings, the following termstake the meaning explicitly associated herein, unless the contextclearly dictates otherwise. The term “herein” refers to thespecification, claims, and drawings associated with the currentapplication. The phrases “in one embodiment,” “in another embodiment,”“in various embodiments,” “in some embodiments,” “in other embodiments,”and other variations thereof refer to one or more features, structures,functions, limitations, or characteristics of the present disclosure,and are not limited to the same or different embodiments unless thecontext clearly dictates otherwise. As used herein, the term “or” is aninclusive “or” operator, and is equivalent to the phrases “A or B, orboth” or “A or B or C, or any combination thereof,” and lists withadditional elements are similarly treated. The term “based on” is notexclusive and allows for being based on additional features, functions,aspects, or limitations not described, unless the context clearlydictates otherwise. In addition, throughout the specification, themeaning of “a,” “an,” and “the” include singular and plural references.

FIG. 1 illustrates a context diagram of an environment for a system thatimplements a blockchain-based state database using a distributed ledger,in accordance with embodiments described herein.

A given area 100 will mostly be covered by two or more mobile networkoperators' wireless networks. Generally, mobile network operators havesome roaming agreements that allow users to roam from home network topartner network under certain conditions, shown in FIG. 1 as homenetwork coverage area 102 and roaming partner network coverage area 104.Operators may configure the mobile user's device, referred to herein asuser equipment (UE), such as UE 106, with priority and a timer to stayon the home network coverage area 102 versus the roaming partner networkcoverage area 104. If a UE (e.g., UE 106) cannot find the home networkcoverage area 102, the UE will scan for a roaming network after a timerexpiration (6 minutes, for example). This could have significant impacton customer experience in case of a catastrophic failure in the network.As shown in FIG. 1 , a 5G RAN is split into DUs (e.g., DU 108) thatmanage scheduling of all the users and a CU that manages the mobilityand radio resource control (RRC) state for all the UEs. The RRC is alayer within the 5G NR protocol stack. It exists only in the controlplane, in the UE and in the gNB. The behavior and functions of RRC aregoverned by the current state of RRC. In 5G NR, RRC has three distinctstates: RRC_IDLE, RRC_CONNECTED and RRC_INACTIVE.

FIG. 2 illustrates a diagram of an example system architecture overviewof a system 200 in which the environment of FIG. 1 may be implemented inaccordance with embodiments described herein.

As shown in FIG. 2 , the radio unit (RU) 206 converts radio signals sentto and from the antenna into a digital signal for transmission overpacket networks. It handles the digital front end (DFE) and the lowerphysical (PHY) layer, as well as the digital beamforming functionality.

The DU 204 may sit close to the RU 206 and runs the radio link control(RLC), the Medium Access Control (MAC) sublayer of the 5G NR protocolstack, and parts of the PHY layer. The MAC sublayer interfaces to theRLC sublayer from above and to the PHY layer from below. The MACsublayer maps information between logical and transport channels.Logical channels are about the type of information carried whereastransport channels are about how such information is carried. Thislogical node includes a subset of the gNB functions, depending on thefunctional split option, and its operation is controlled by the CU 202.

The CU 202 is the centralized unit that runs the RRC and Packet DataConvergence Protocol (PDCP) layers. A gNB may comprise a CU and one DUconnected to the CU via Fs-C and Fs-U interfaces for control plane (CP)and user plane (UP), respectively. A CU with multiple DUs will supportmultiple gNBs. The split architecture enables a 5G network to utilizedifferent distribution of protocol stacks between CU 202 and DU 204depending on mid-haul availability and network design. The CU 202 is alogical node that includes the gNB functions like transfer of user data,mobility control, RAN sharing, positioning, session management, etc.,with the exception of functions that may be allocated exclusively to theDU 204. The CU 202 controls the operation of several DUs 204 over themid-haul interface.

As mentioned above, 5G network functionality is split into twofunctional units: the DU 204, responsible for real time 5G layer 1 (L1)and 5G layer 2 (L2) scheduling functions, and the CU 202 responsible fornon-real time, higher L2 and 5G layer 3 (L3). As shown in FIG. 2 , theDU's server and relevant software may be hosted on a cell site 216itself or can be hosted in an edge cloud (local data center (LDC) 218 orcentral office) depending on transport availability and fronthaulinterface. The CU's server and relevant software may be hosted in aregional cloud data center or, as shown in FIG. 2 , in a breakout edgedata center (B-EDC) 214. As shown in FIG. 2 , the DU 204 may beprovisioned to communicate via a pass-through edge data center (P-EDC)208. The P-EDC 208 may provide a direct circuit fiber connection fromthe DU directly to the primary cloud availability zone (e.g., B-EDC 214)hosting the CU 202. In some embodiments, the LDC 218 and P-EDC 208 maybe co-located or in a single location. The CU 202 may be connected to aregional cloud data center (RDC) 210, which in turn may be connected toa national cloud data center (NDC) 212. In the example embodiment, theP-EDC 208, the LDC 218, the cell site 216 and the RU 206 may all bemanaged by the mobile network operator and the B-EDC 214, the RDC 210and the NDC 212 may all be managed by a cloud computing serviceprovider. According to various embodiments, the actual split between DUand RU may be different depending on the specific use-case andimplementation.

FIG. 3 is a diagram showing connectivity between certaintelecommunication network components during cellular telecommunicationin accordance with embodiments described herein.

The central unit control plane (CU-CP) 302, for example, of CU 110 ofFIG. 1 or CU 202 of FIG. 2 , primarily manages control processing ofDUs, such as DU 308, and UEs, such as UE 306. The CU-CP 302 hosts RRCand the control-plane part of the PDCP protocol. CU-CP 302 manages themobility and radio resource control (RRC) state for all the UEs. The RRCis a layer within the 5G NR protocol stack and manages context andmobility for all UEs. The behavior and functions of RRC are governed bythe current state of RRC. In 5G NR, RRC has three distinct states:RRC_IDLE, RRC_CONNECTED and RRC_INACTIVE. The CU-CP 302 terminates theE1 interface connected with the central unit user plane (CU-UP) 304 andthe F1-C interface connected with the DU 308. The DU 308 maintains aconstant heartbeat with CU-CP 302. The CU-UP 304 manages the datasessions for all UEs 306 and hosts the user plane part of the PDCPprotocol. The CU-UP 304 terminates the E1 interface connected with theCU-CP and the F1-U interface connected with the DU 308.

A virtual private cloud is a configurable pool of shared resourcesallocated within a public cloud environment. The VPC provides isolationbetween one VPC user and all other users of the same cloud, for example,by allocation of a private IP subnet and a virtual communicationconstruct (e.g., a VLAN or a set of encrypted communication channels)per user. In some embodiments, this 5G network leverages the distributednature of 5G cloud-native network functions and cloud flexibility, whichoptimizes the placement of 5G network functions for optimal performancebased on latency, throughput and processing requirements.

In some embodiments, the network architecture utilizes a logicalhierarchical architecture consisting of National Data Centers (NDCs),Regional Data Centers (RDCs) and Breakout Edge Data Centers (BEDCs), toaccommodate the distributed nature of 5G functions and the varyingrequirements for service layer integration. In one or more embodiments,BEDCs are deployed in Local Zones hosting 5G NFs that have strictlatency budgets. They may also be connected with Passthrough Edge DataCenters (PEDC), which serve as an aggregation point for all Local DataCenters (LDCs) and cell sites in a particular market. BEDCs also provideinternet peering for 5G data service.

In one or more embodiments, an O-RAN network may be implemented thatincludes an RU (Radio Unit), which is deployed on towers and a DU(Distributed Unit), which controls the RU. These units interface withthe Centralized Unit (CU), which is hosted in the BEDC at the LocalZone. These combined pieces provide a full RAN solution that handles allradio level control and subscriber data traffic.

In some embodiments, the User Plane Function (Data Network Name (DNN))is collocated in the BEDC, which anchors user data sessions and routesto the internet. In another aspect, the BEDCs leverage local internetaccess available in Local Zones, which allows for a better userexperience while optimizing network traffic utilization.

In one of more embodiments, the Regional Data Centers (RDCs) are hostedin the Region across multiple availability zones. The RDCs host 5Gsubscribers' signaling processes such as authentication and sessionmanagement as well as voice for 5G subscribers. These workloads canoperate with relatively high latencies, which allows for a centralizeddeployment throughout a region, resulting in cost efficiency andresiliency. For high availability, multiple RDCs are deployed in aregion, each in a separate Availability Zone (AZ) to ensure applicationresiliency and high availability.

In another aspect of some embodiments, an AZ is one or more discretedata centers with redundant power, networking, and connectivity in aRegion. In some embodiments, AZs in a Region are interconnected withhigh-bandwidth and low-latency networking over a fully redundant,dedicated metro fiber, which provides high-throughput, low-latencynetworking between AZs.

Cloud Native Functions (CNFs) deployed in the RDC utilize a high speedbackbone to failover between AZs for application resiliency. CNFs likeAMF and SMF, which are deployed in RDC, continue to be accessible fromthe BEDC in the Local Zone in case of an AZ failure. They serve as thebackup CNF in the neighboring AZ and would take over and service therequests from the BEDC.

In this embodiment of the system for implementing a blockchain-basedstate database using a distributed ledger, dedicated VPCs areimplemented for each Data Center type (e.g., local data center, breakoutedge data center, regional data center, national data center, and thelike). In some such embodiments, the national data center VPC stretchesacross multiple Availability Zones (AZs). In another aspect of someembodiments, two or more AZs are implemented per region of the cloudcomputing service provider.

Some embodiments of the 5G Core network functions require support foradvanced routing capabilities inside VPC and across VPCs (e.g., UPF, SMFand ePDG). These functions rely on routing protocols such as BGP forroute exchange and fast failover (both stateful and stateless). Tosupport these requirements, virtual routers are deployed on EC2 toprovide connectivity within and across VPCs, as well as back to theon-prem network.

Referring now to FIGS. 4A-6 , interactions between computer componentsmay usually be described as either stateful or stateless. For example,stateful services keep track of sessions or transactions and reactdifferently to the same inputs based on that history. In contrast,stateless services rely on clients to maintain sessions and centeraround operations that manipulate resources, rather than the state.Telephony, and communication in general, is typically a statefulinteraction.

In this manner, stateful computer architecture typically storesadditional information server-side, recording the state of the currenttransaction and waiting for the next instructions. Continuing, instateful computer architecture a server is required to save informationabout a session or previous transactions. Since this information isstored on the server, these systems typically do not handle crashes wellsince access to the saved information is lost. In such a scenario, auser would have to log out and start over at the beginning of thesession or transaction.

In contrast, stateless computer architecture typically stores additionalinformation on the client-side, and passes along additional informationwith each step. This additional information may be described as“reminding” the server of the previous steps that have occurred. Assuch, in stateless computer architecture, the server does not have toretain information about the state. As such, these systems typicallyhandle crashes well since the user's transactions may simply betransferred over to a new server.

For 5G telephony communication state information is required for manycellular telephone communication activities. For example, stateinformation is needed to hand off from one cellular tower to anothercellular tower. In this regard, without state information an end userwill be stuck at a cellular site and unable to transfer to another site.Additionally, state information is needed to make a phone call.Furthermore, state information is needed to keep from dropping a call.Moreover, state information is needed to send billing information.

Thus, when a connection loss or other type of failure occurs, thestateful 5G end user mobile devices are severely compromised in theirability to carry out any significant cellular telephone communicationactivities. Accordingly, the disclosed embodiments of the systemimplement a blockchain-based state database using a distributed ledgerto record and store the state information of the 5G end user mobiledevices in the blockchain. Thus, the 5G end user mobile devices are ableto maintain their state after a connection loss with the server, or whenanother type of failure occurs, using the state information in theblockchain-based state database recorded on the distributed ledger. Theblockchain-based state database recorded on the distributed ledger isable to recreate the state for either single 5G end user or multiple 5Gend users.

FIG. 4A illustrates a system for implementing a blockchain-based statedatabase using a distributed ledger that includes a Unified DataManagement System 410, central distributed subscriber database 412, aplurality of connected 5G Cores 420, 430, 440, 450, and 460, and aplurality of 5G end user mobile devices 422, 424, 426, 432, 434, 436,442, 444, 446, 452, 454, 456, 462, 464, and 466. The central distributedsubscriber database 412 is contained in the Unified Data ManagementSystem 410. The plurality of connected 5G Cores 420, 430, 440, 450, and460 are each connected to the central distributed subscriber database412 by connection lines 428, 438, 448, 458, and 468. The connectionlines 428, 438, 448, 458, and 468 transmit voice and data information aswell as control information, between the central distributed subscriberdatabase 412 and the plurality of connected 5G Cores 420, 430, 440, 450,and 460. This information also includes recorded state information ofthe 5G end user mobile devices that is transmitted between the centraldistributed subscriber database 412 and the plurality of 5G end usermobile devices 422, 424, 426, 432, 434, 436, 442, 444, 446, 452, 454,456, 462, 464, and 466. Additionally, the plurality of 5G end usermobile devices 422, 424, 426, 432, 434, 436, 442, 444, 446, 452, 454,456, 462, 464, and 466 are each connected to their respective 5G Cores420, 430, 440, 450, and 460. In some embodiments this is a directconnection, while in other embodiments, there are additional telephonycomponents (e.g., antennas, receivers, and the like) that bridge theconnection between the plurality of 5G end user mobile devices 422, 424,426, 432, 434, 436, 442, 444, 446, 452, 454, 456, 462, 464, and 466 thatare each connected to their respective 5G Cores 420, 430, 440, 450, and460.

Referring now to FIG. 4B, the system of FIG. 4A is again shown forimplementing a blockchain-based state database using a distributedledger. However, in this embodiment, the central distributed subscriberdatabase 412 has lost connection with one of the 5G Cores 420, due to adisruption in connection line 428. There may be various reasons for sucha lost connection that include, by way of example only, and not by wayof limitation, large scale power failure, local outages, physical damageto a component, planned maintenance, unplanned component failure, andthe like. In some such systems, the plurality of 5G Cores 420, 430, 440,450, and 460 are each configured so that they are able to independentlymaintain operations for their respective 5G end user mobile devices 422,424, 426, 432, 434, 436, 442, 444, 446, 452, 454, 456, 462, 464, and 466after a connection loss by using a local copy of the informationnecessary for operation.

Referring now to FIG. 4C, the system of FIG. 4A is again shown forimplementing a blockchain-based state database using a distributedledger. However, in this embodiment, the central distributed subscriberdatabase 412 has been able to re-reestablish connection with the one ormore 5G end user mobile devices that had previously lost its connectionwith the distributed subscriber database. Thus, the plurality of 5G enduser mobile devices 422, 424, 426, 432, 434, 436, 442, 444, 446, 452,454, 456, 462, 464, and 466 are each configured so that they are able touse the state information from the state database recorded in thedistributed ledger of the blockchain to maintain operations for the 5Gend user mobile devices. Nevertheless, while the connection line 428 maynow be successfully transmitting voice and data information, as well ascontrol information, between the central distributed subscriber database412 and the 5G Core 420, there may now be missing state information dueto the time that the one or more 5G end user mobile devices weredisconnected from the central distributed subscriber database 412.

In some embodiments of the system for implementing a blockchain-basedstate database using a distributed ledger, each individual 5G end usermobile device 422, 424, 426, 432, 434, 436, 442, 444, 446, 452, 454,456, 462, 464, and 466 is connected to its associated 5G Core 420, 430,440, 450, and 460 using an IMSI (International Mobile SubscriberIdentifier) number. An IMSI is a unique number associated with GlobalSystem for Mobile Communications (GSM) and Universal MobileTelecommunications System (UMTS) network mobile phone users. As such,the IMSI is a unique number that identifies a mobile end user that is asubscriber to the carrier network.

In another aspect of some embodiments of the system, a mobile subscriberof each individual end user mobile device is identified by its SIM(Subscriber Identity Module) card. A SIM card is a smart card inside amobile phone that includes an identification number that is unique tothe owner of the end user mobile device. The SIM card may store personaldata and prevent operation if it is removed. The SIM card may alsoinclude an authentication key that is used to authenticate the owner ofthe end user mobile device. Additionally, the SIM card includes aprocessor, memory, and security circuits.

In another aspect of the system for implementing a blockchain-basedstate database using a distributed ledger, distributed keyauthentication may be used to authenticate the 5G Cores 420, 430, 440,450, and 460, the 5G end user mobile devices 422, 424, 426, 432, 434,436, 442, 444, 446, 452, 454, 456, 462, 464, and 466, or both. In someembodiments, the distributed keys are placed in the distributed ledgerblockchain with the recorded state information of the one or more 5G enduser mobile devices, instead of in the SIM cards of the 5G end usermobile devices. Thus, in such embodiments, the 5G end user mobiledevices 422, 424, 426, 432, 434, 436, 442, 444, 446, 452, 454, 456, 462,464, and 466 employ blockchain-based authentication, instead of SIMcard-based authentication. In still other embodiments, the distributedkeys are placed in the distributed ledger blockchain, instead of in theSIM cards of the 5G end user mobile devices, and the system does notrecord the state information of the 5G end user mobile devices in astate database with the distributed ledger blockchain. In suchembodiments, the 5G end user mobile devices 422, 424, 426, 432, 434,436, 442, 444, 446, 452, 454, 456, 462, 464, and 466 still employblockchain-based authentication, instead of SIM card-basedauthentication, but the blockchain-based state database is not employed.

Referring now to FIG. 5 , a logic diagram is shown that displays theprocess of the state information being uploaded to the distributedledger of the blockchain that is then available to the 5G end usermobile devices. In some embodiments of this 5G system architecture, atoperation 510, state information is sent to the blockchain distributedledger as back-up for the 5G end user mobile devices. At operation 520,the transaction is represented online as a block. At operation 530, theblock is broadcast to every 5G mobile end user device in the network. Atoperation 540, the 5G end user mobile devices verify the transaction. Atoperation 550, the block is added to the chain of all priortransactions. At operation 560, the State Information can be moved toany 5G mobile end user device that loses its State due to losingconnection with the distributed subscription database.

FIG. 6 is a logic diagram showing the system for implementing ablockchain-based state database using a distributed ledger. As shown inFIG. 6 , at operation 610, a Unified Data Management System 410 isprovided that connects to a plurality of 5G cores, and each 5G core inturn connects to individual 5G end user mobile devices. At operation620, state information of one or more 5G end user mobile devices isrecorded in a state database using the distributed ledger of theblockchain. At operation 630, a connection is lost with the centraldistributed subscriber database 412. At operation 640, a lost connectionbetween one or more 5G end user mobile devices and the centraldistributed subscriber database 412 is reconnected. At operation 650,the recorded states are accessed of the one or more 5G end user mobiledevices in the state database on the distributed ledger of theblockchain. At operation 660, the recorded states of the one or more 5Gend user mobile devices are reestablished using the recorded states fromthe state database in the distributed ledger of the blockchain.

FIG. 7 shows a system diagram that describes an example implementationof a computing system(s) for implementing embodiments described herein.The functionality described herein for implementing a blockchain-basedstate database using a distributed ledger can be implemented either ondedicated hardware, as a software instance running on dedicatedhardware, or as a virtualized function instantiated on an appropriateplatform, e.g., a cloud infrastructure. In some embodiments, suchfunctionality may be completely software-based and designed ascloud-native, meaning that they're agnostic to the underlying cloudinfrastructure, allowing higher deployment agility and flexibility.

In particular, shown is example host computer system(s) 701. Forexample, such computer system(s) 701 may represent those in various datacenters and cell sites shown and/or described herein that host thefunctions, components, microservices and other aspects described hereinto implement a system for a blockchain-based state database using adistributed ledger. In some embodiments, one or more special-purposecomputing systems may be used to implement the functionality describedherein. Accordingly, various embodiments described herein may beimplemented in software, hardware, firmware, or in some combinationthereof. Host computer system(s) 701 may include memory 702, one or morecentral processing units (CPUs) 714, I/O interfaces 718, othercomputer-readable media 720, and network connections 722.

Memory 702 may include one or more various types of non-volatile and/orvolatile storage technologies. Examples of memory 702 may include, butare not limited to, flash memory, hard disk drives, optical drives,solid-state drives, various types of random-access memory (RAM), varioustypes of read-only memory (ROM), other computer-readable storage media(also referred to as processor-readable storage media), or the like, orany combination thereof. Memory 702 may be utilized to storeinformation, including computer-readable instructions that are utilizedby CPU 714 to perform actions, including those of embodiments describedherein.

Memory 702 may have stored thereon control module(s) 704. The controlmodule(s) 704 may be configured to implement and/or perform some or allof the functions of the systems, components and modules described hereinfor implementing a blockchain-based state database using a distributedledger. Memory 702 may also store other programs and data 710, which mayinclude rules, databases, application programming interfaces (APIs),software platforms, cloud computing service software, network managementsoftware, network orchestrator software, network functions (NF), Al orML programs or models to perform the functionality described herein,user interfaces, operating systems, other network management functions,other NFs, etc.

Network connections 722 are configured to communicate with othercomputing devices to facilitate the functionality described herein. Invarious embodiments, the network connections 722 include transmittersand receivers (not illustrated), cellular telecommunication networkequipment and interfaces, and/or other computer network equipment andinterfaces to send and receive data as described herein, such as to sendand receive instructions, commands and data to implement the processesdescribed herein. I/O interfaces 718 may include a video interface,other data input or output interfaces, or the like. Othercomputer-readable media 720 may include other types of stationary orremovable computer-readable media, such as removable flash drives,external hard drives, or the like.

The various embodiments described above can be combined to providefurther embodiments. These and other changes can be made to theembodiments in light of the above-detailed description. In general, inthe following claims, the terms used should not be construed to limitthe claims to the specific embodiments disclosed in the specificationand the claims, but should be construed to include all possibleembodiments along with the full scope of equivalents to which suchclaims are entitled. Accordingly, the claims are not limited by thedisclosure.

1. A method for implementing a blockchain-based state database using adistributed ledger, the method comprising: providing, by a mobilenetwork operator, a distributed unit (DU) of a fifth-generation NewRadio (5G NR) cellular telecommunication network radio access network(RAN) that is served by a particular 5G NR cellular site base station,wherein the DU: is associated with a primary 5G NR Next Generation NodeB (gNB) identified by a primary identifier (ID); and is in operablecommunication with a corresponding primary central unit control plane(CU-CP) of a 5G NR primary centralized unit (CU) that is hosted on acloud-native virtualized compute instance in a primary cloudavailability zone and is also associated with the primary gNB identifiedby the primary ID; providing a Unified Data Management system thatincludes a Distributed Subscriber Database and connects to a pluralityof 5G Cores, wherein each 5G Core in turn connects to one or more 5G enduser mobile devices; recording states of one or more 5G end user mobiledevices in any 5G network RAN or Core element in a state database usingthe distributed ledger of the blockchain; in response to a lostconnection of a network element, restoring, using the blockchaindatabase, the lost connection of the network element to the networkwithout any interaction with the 5G end user mobile device; accessingthe recorded states of the one or more 5G end user mobile devices in thestate database on the distributed ledger of the blockchain; andreestablishing the recorded states of the one or more 5G end user mobiledevices using the recorded states from the state database in thedistributed ledger of the blockchain.
 2. The method of claim 1 furthercomprising: connecting each individual 5G end user mobile device to anassociated 5G Core using an IMSI (International Mobile SubscriberIdentifier) number.
 3. The method of claim 1, further comprising:identifying a mobile subscriber of each individual 5G end user mobiledevice by its SIM (Subscriber Identity Module) card.
 4. The method ofclaim 1, wherein the blockchain-based state database is optimized forperformance.
 5. The method of claim 1, wherein the blockchain-basedstate database is optimized for reliability.
 6. The method of claim 1,wherein distributed key authentication is used to authenticate the 5GCores.
 7. The method of claim 1, wherein distributed keys are placed inthe blockchain with the state information from the DistributedSubscriber Database, instead of the 5G Cores.
 8. A system thatimplements a blockchain-based state database using a distributed ledger,the system comprising: a memory that stores computer executableinstructions; and a processor that executes the computer executableinstructions to cause operations to be performed, the operationsincluding: provide, by a mobile network operator, a distributed unit(DU) of a fifth-generation New Radio (5G NR) cellular telecommunicationnetwork radio access network (RAN) that is served by a particular 5G NRcellular site base station, wherein the DU: is associated with a primary5G NR Next Generation Node B (gNB) identified by a primary identifier(ID); and is in operable communication with a corresponding primarycentral unit control plane (CU-CP) of a 5G NR primary centralized unit(CU) that is hosted on a cloud-native virtualized compute instance in aprimary cloud availability zone and is also associated with the primarygNB identified by the primary ID; provide a Unified Data Managementsystem that includes a Distributed Subscriber Database and connects to aplurality of 5G Cores, wherein each 5G Core in turn connects to one ormore 5G end user mobile devices; record states of one or more 5G enduser mobile devices in any 5G network RAN or Core element in a statedatabase using the distributed ledger of the blockchain; in response toa lost connection of a network element, restore, using the blockchaindatabase, the lost connection of the network element to the networkwithout any interaction with the 5G end user mobile device; access therecorded states of the one or more 5G end user mobile devices in thestate database on the distributed ledger of the blockchain; andreestablish the recorded states of the one or more 5G end user mobiledevices using the recorded states from the state database in thedistributed ledger of the blockchain.
 9. The system of claim 8, furthercomprising: connecting each individual 5G end user mobile device to anassociated 5G Core using an IMSI (International Mobile SubscriberIdentifier) number.
 10. The system of claim 8, further comprising:identifying a mobile subscriber of each individual 5G end user mobiledevice by its SIM (Subscriber Identity Module) card.
 11. The system ofclaim 8, wherein the blockchain-based state database is optimized forperformance.
 12. The system of claim 8, wherein the blockchain-basedstate database is optimized for reliability.
 13. The system of claim 8,wherein distributed key authentication is used to authenticate the 5GCores.
 14. The system of claim 8, wherein distributed keys are placed inthe blockchain with the state information from the DistributedSubscriber Database, instead of the 5G Cores.
 15. A non-transitorycomputer-readable storage medium having computer-executable instructionsstored thereon that, when executed by a processor, cause the processorto: provide a Unified Data Management system that includes a DistributedSubscriber Database and connects to a plurality of 5G Cores, whereineach 5G Core in turn connects to one or more 5G end user mobile devices;record states of one or more 5G end user mobile devices in any 5Gnetwork RAN or Core element in a state database using the distributedledger of the blockchain; in response to a lost connection of a networkelement, restore, using the blockchain database, the lost connection ofthe network element to the network without any interaction with the 5Gend user mobile device; access the recorded states of the one or more 5Gend user mobile devices in the state database on the distributed ledgerof the blockchain; and reestablish the recorded states of the one ormore 5G end user mobile devices using the recorded states from the statedatabase in the distributed ledger of the blockchain.
 16. Thenon-transitory computer-readable storage medium of claim 15, wherein thecomputer-executable instructions, when executed by a processor, furthercause the processor to: connect each individual 5G end user mobiledevice to an associated 5G Core using an IMSI (International MobileSubscriber Identifier) number.
 17. The non-transitory computer-readablestorage medium of claim 15, wherein the computer-executableinstructions, when executed by a processor, further cause the processorto: identify a mobile subscriber of each individual 5G end user mobiledevice by a SIM (Subscriber Identity Module) card of the end user mobiledevice.
 18. The non-transitory computer-readable storage medium of claim15, wherein the blockchain-based state database is optimized for one ormore of performance and reliability.
 19. The non-transitorycomputer-readable storage medium of claim 15, wherein distributed keyauthentication is used to authenticate the 5G Cores.
 20. Thenon-transitory computer-readable storage medium of claim 15, whereindistributed keys are placed in the blockchain with the state informationfrom the Distributed Subscriber Database, instead of the 5G Cores.